約 5,663,963 件
https://w.atwiki.jp/gamedev55/pages/61.html
■http //unity3d.com/unity/download/download-windows Unity 4.0.0f7 UnitySetup-4.0.0.exe 645 MB (677,037,872 バイト) 要2.3GB 、、、ファイルがでかいなぁ ■「Activate the free version of Unity」 、、、↑セットアップの途中で選ぶ。 ■「ブロック崩し」のチュートリアル http //japan.unity3d.com/developer/document/tutorial/my-first-unity/01.html ■Unity Script Reference http //docs.unity3d.com/Documentation/ScriptReference/ ・Runtime Classes http //docs.unity3d.com/Documentation/ScriptReference/20_class_hierarchy.html ■DontGoThroughThings http //wiki.unity3d.com/index.php?title=DontGoThroughThings
https://w.atwiki.jp/cohstatsjp/pages/217.html
Infantry Commandos Contents 1 British Veterancy 2 Tactics 3 History 4 Called In Using 4.1 Glider 5 Squad Abilities 5.1 Commando Throw Grenade 5.2 Concealing Smoke 6 Squad Weapons 6.1 Sten SMG 6.2 Commando Demolitions Charge 6.3 Commando Grenade Commandos Squad Size 6 Capture Rate 1 Sup Threshold 0.35 Health 390 Sight 35 Pin Threshold 0.8 Cost 510 Detection 7/0 Recovery Rate 0.012 Hotkey C Population 6 Time 36 Retreat Modifier 0.5 Target Type infantry_soldier Upkeep 9.0144 Reinforce Cost 0.4119 Critical Type infantry Squad Slots 6 Reinforce Time 1.5 British Veterancy british units, excluding the Lieutenant, captain, and command tank, do not gain veterancy. Any experiences earned from kills by infantry are transfered to nearby officers at the time of the kill, or otherwise lost forever. Commandos do not benefit from the presence of a Lieutenant or captain, but will still transfer earned experience Tactics Commandos can only be used with the Royal Commandos Doctrine. Commandos are good counters to enemy machine guns as they can drop outside the HMG s fire arc with gliders or can deploy smoke to make them untargetable for 7 seconds. Never drop the glider near the presence of a sighted Marder III or StuG as they automatically target the glider even before the Commandos exit. This applies also to the Tetrarch Glider. Use Commandos against enemy infantry. They can also be used for capping power as they can drop behind enemy lines and do not have a movement handicap when in enemy territory. Drop the Commandos near an important strategic point to capture it, or near the main base to wreck havoc in your enemies base and turn his focus. Problems with gliders landing behind your lines and commandos wrecking your day? Cover vacant fields, long roads, and other great landing spots in dragon s teeth, they will tear up the glider before the troops can spawn. If an enemy drops a Panzershreck, pick it up with the commando squad as soon as possible. It makes them good against their usual counters - armored cars and light tanks. History The Air landing troops of the British Airborne were tasked with assaulting German positions prior to the D-Day landings. They landed their gliders in Coup de Main assaults on enemy positions, surprising the German defenders in risky attacks. They were all volunteers, and well-trained for their dangerous job, and continued to act as elite ground infantry once the airborne operations were over. The Commandos in Company of Heroes are actually Air landing troops from an Airborne Division, or SAS (Special Air Service) Commandos. Their distinctive red berets indicate they re airborne troops or SAS Troops, as Commandos wore green berets. Commandos came from several branches (Royal Army Commandos, Royal Marine Commandos, and Royal Navy Commandos) and none were involved in glider operations. Called In Using Glider [Expand][Hide] Cost 560 Activation targeted Duration _ Target tp_position Recharge 75 Hotkey Effects Call in a glider full of Commandos. The glider is capable of producing and reinforcing more Commandos in territory. ESee Ability Glider for details. Squad Abilities Commando Throw Grenade [Expand][Hide] Cost 25 Activation targeted Duration _ Target tp_any Recharge 30 Hotkey N Effects The Squad will throw a Mk2 Pineapple Grenade. ESee Ability Commando Throw Grenade for details. Concealing Smoke [Expand][Hide] Cost Activation timed Duration 14 Target tp_any Recharge 30 Hotkey S Effects Break any suppression or pinning effects on the squad and envelope the Commandos in concealing smoke. ESee Ability Concealing Smoke for details. Squad Weapons Sten SMG [Expand][Hide] Weapon Sten SMG See Weapon Sten SMG for details. Commando Demolitions Charge [Expand][Hide] Weapon Commando Demolitions Charge See Weapon Commando Demolitions Charge for details. Commando Grenade [Expand][Hide] Weapon Commando Grenade See Weapon Commando Grenade for details. Retrieved from http //coh-stats.com/Infantry Commandos
https://w.atwiki.jp/usb_audio/pages/35.html
原文：Audio Device Document 1.0(PDF) USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 36 4 Descriptors The following sections describe the standard and class-specific USB descriptors for the Audio Interface Class. 4.1 Device Descriptor Because audio functionality is always considered to reside at the interface level, this class specification does not define a specific audio device descriptor. For audio-only devices, the device descriptor must indicate that class information is to be found at the interface level. Therefore, the bDeviceClass field of the device descriptor must contain zero so that enumeration software looks down at the interface level to determine the Interface Class. The bDeviceSubClass and bDeviceProtocol fields must be set to zero. All other fields of the device descriptor must comply with the definitions in Section 9.6.1, “Descriptor” of the USB Specification. There is no class-specific device descriptor. 4.2 Configuration Descriptor In analogy to the device descriptor, an audio configuration descriptor is applicable only in the case of audio-only devices. It is identical to the standard configuration descriptor defined in Section 9.6.2, “Configuration” of the USB Specification. There is no class-specific configuration descriptor. 4.3 AudioControl Interface Descriptors The AudioControl (AC) interface descriptors contain all relevant information to fully characterize the corresponding audio function. The standard interface descriptor characterizes the interface itself, whereas the class-specific interface descriptor provides pertinent information concerning the internals of the audio function. It specifies revision level information and lists the capabilities of each Unit and Terminal. 4.3.1 Standard AC Interface Descriptor The standard AC interface descriptor is identical to the standard interface descriptor defined in Section 9.6.3, “Interface” of the USB Specification, except that some fields have now dedicated values. Table 4-1 Standard AC Interface Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 9 1 bDescriptorType 1 Constant INTERFACE descriptor type 2 bInterfaceNumber 1 Number Number of interface. A zero-based value identifying the index in the array of concurrent interfaces supported by this configuration. 3 bAlternateSetting 1 Number Value used to select an alternate setting for the interface identified in the prior field. |4|bNumEndpoints|1|Number|Number of endpoints used by this interface (excluding endpoint 0). This number is either 0 or 1 if the optional status interrupt endpoint is present.| USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 37 Offset Field Size Value Description 5 bInterfaceClass 1 Class AUDIO. Audio Interface Class code (assigned by the USB). See Section A.1, “Audio Interface Class Code.” 6 bInterfaceSubClass 1 Subclass AUDIOCONTROL. Audio Interface Subclass code. Assigned by this specification. See Section A.2, “Audio Interface Subclass Codes.” 7 bInterfaceProtocol 1 Protocol Not used. Must be set to 0. 8 iInterface 1 Index Index of a string descriptor that describes this interface. dummy 4.3.2 Class-Specific AC Interface Descriptor The class-specific AC interface descriptor is a concatenation of all the descriptors that are used to fully describe the audio function, i.e. all Unit Descriptors (UDs) and Terminal Descriptors (TDs). The total length of the class-specific AC interface descriptor depends on the number of Units and Terminals in the audio function. Therefore, the descriptor starts with a header that reflects the total length in bytes of the entire class-specific AC interface descriptor in the wTotalLength field. The bcdADC field identifies the release of the Audio Device Class Specification with which this audio function and its descriptors are compliant. The bInCollection field indicates how many AudioStreaming and MIDIStreaming interfaces there are in the Audio Interface Collection to which this AudioControl interface belongs. The baInterfaceNr() array contains the interface numbers of all the AudioStreaming and MIDIStreaming interfaces in the Collection. The bInCollection and baInterfaceNr() fields together provide all necessary information to determine which interfaces together constitute the entire USB interface to the audio function, i.e. describe the Audio Interface Collection. The order in which the Unit and Terminal descriptors are reported is not important because every descriptor can be identified through its bDescriptorType and bDescriptorSubtype field. The bDescriptorType field identifies the descriptor as being a class-specific interface descriptor. The bDescriptorSubtype field further qualifies the exact nature of the descriptor. The following table defines the class-specific AC interface header descriptor. Table 4-2 Class-Specific AC Interface Header Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 8+n 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant HEADER descriptor subtype. 3 bcdADC 2 BCD Audio Device Class Specification Release Number in Binary-Coded Decimal. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 38 Offset Field Size Value Description 5 wTotalLength 2 Number Total number of bytes returned for the class-specific AudioControl interface descriptor. Includes the combined length of this descriptor header and all Unit and Terminal descriptors. 7 bInCollection 1 Number The number of AudioStreaming and MIDIStreaming interfaces in the Audio Interface Collection to which this AudioControl interface belongs n 8 baInterfaceNr(1) 1 Number Interface number of the first AudioStreaming or MIDIStreaming interface in the Collection. … … … … … 8+(n-1) baInterfaceNr(n) 1 Number Interface number of the last AudioStreaming or MIDIStreaming interface in the Collection. This header is followed by one or more Unit and/or Terminal Descriptors. The layout of the descriptors depends on the type of Unit or Terminal they represent. There are seven types of Unit and Terminal Descriptors possible. They are summarized in the following sections. The first four fields are common for all Unit and Terminal Descriptors. They contain the Descriptor Length, Descriptor Type, Descriptor Subtype, and Unit or Terminal ID. Each Unit and Terminal within the audio function is assigned a unique identification number, the Unit ID (UID) or Terminal ID (TID), contained in the bUnitID or bTerminalID field of the descriptor. The value 0x00 is reserved for undefined ID, effectively restricting the total number of addressable Entities in the audio function (both Units and Terminals) to 255. Besides uniquely identifying all addressable Entities in an audio function, the IDs also serve to describe the topology of the audio function; i.e. the bSourceID field of a Unit or Terminal descriptor indicates to which other Unit or Terminal this Unit or Terminal is connected. 4.3.2.1 Input Terminal Descriptor The Input Terminal descriptor (ITD) provides information to the Host that is related to the functional aspects of the Input Terminal. The Input Terminal is uniquely identified by the value in the bTerminalID field. No other Unit or Terminal within the same alternate setting of the AudioControl interface may have the same ID. This value must be passed in the TerminalID field of each request that is directed to the Terminal. The wTerminalType field provides pertinent information about the physical entity that the Input Terminal represents. This could be a USB OUT endpoint, an external Line In connection, a microphone, etc. A complete list of Terminal Type codes is provided in a separate document, USB Audio Terminal Types, that is considered part of this specification. The bAssocTerminal field is used to associate an Output Terminal to this Input Terminal, effectively implementing a bi-directional Terminal pair. If the bAssocTerminal field is used, both associated Terminals must belong to the bi-directional Terminal Type group. If no association exists, the bAssocTerminal field must be set to zero. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 39 The Host software can treat the associated Terminals as being physically related. In many cases, one Terminal can not exist without the other. A typical example of such a Terminal pair is an Input Terminal, which represents the microphone, and an Output Terminal, which represents the earpiece of a headset. The bNrChannels, wChannelConfig and iChannelNames fields together constitute the cluster descriptor. They characterize the cluster that leaves the Input Terminal over the single Output Pin (‘downstream’ connection). For a detailed description of the cluster descriptor, see Section 3.7.2.3, “Audio Channel Cluster Format.” An index to a string descriptor is provided to further describe the Input Terminal. The following table presents an outline of the Input Terminal descriptor. Table 4-3 Input Terminal Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 12 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant INPUT_TERMINAL descriptor subtype. 3 bTerminalID 1 Constant Constant uniquely identifying the Terminal within the audio function. This value is used in all requests to address this Terminal. 4 wTerminalType 2 Constant Constant characterizing the type of Terminal. See USB Audio Terminal Types. 6 bAssocTerminal 1 Constant ID of the Output Terminal to which this Input Terminal is associated. 7 bNrChannels 1 Number Number of logical output channels in the Terminal’s output audio channel cluster. 8 wChannelConfig 2 Bitmap Describes the spatial location of the logical channels. 10 iChannelNames 1 Index Index of a string descriptor, describing the name of the first logical channel. 11 iTerminal 1 Index Index of a string descriptor, describing the Input Terminal. 4.3.2.2 Output Terminal Descriptor The Output Terminal descriptor (OTD) provides information to the Host that is related to the functional aspects of the Output Terminal. The Output Terminal is uniquely identified by the value in the bTerminalID field. No other Unit or Terminal within the same alternate setting of the AudioControl interface may have the same ID. This value must be passed in the UnitID field of each request that is directed to the Terminal. The wTerminalType field provides pertinent information about the physical entity the Output Terminal represents. This could be a USB IN endpoint, an external Line Out connection, a speaker system etc. A USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 40 complete list of Terminal Type codes is provided in a separate document, USB Audio Terminal Types that is considered part of this specification. The bAssocTerminal field is used to associate an Input Terminal to this Output Terminal, effectively implementing a bi-directional Terminal pair. If the bAssocTerminal field is used, both associated Terminals must belong to the bi-directional Terminal Type group. If no association exists, the bAssocTerminal field must be set to zero. The Host software can treat the associated Terminals as being physically related. In many cases, one Terminal can not exist without the other. A typical example of such a Terminal pair is an Input Terminal, which represents the microphone, and an Output Terminal, which represents the earpiece of a headset. The bSourceID field is used to describe the connectivity for this Terminal. It contains the ID of the Unit or Terminal to which this Output Terminal is connected via its Input Pin. The cluster descriptor, describing the logical channels entering the Output Terminal is not repeated here. It is up to the Host software to trace the connection ‘upstream’ to locate the cluster descriptor pertaining to this audio channel cluster. An index to a string descriptor is provided to further describe the Output Terminal. The following table presents an outline of the Output Terminal descriptor. Table 4-4 Output Terminal Descriptor Offset Field Size Value Description 0 bLength 1 Number Size of this descriptor, in bytes 9 1 bDescriptorType 1 Constant CS_INTERFACE descriptor type. 2 bDescriptorSubtype 1 Constant OUTPUT_TERMINAL descriptor subtype. 3 bTerminalID 1 Constant Constant uniquely identifying the Terminal within the audio function. This value is used in all requests to address this Terminal. 4 wTerminalType 2 Constant Constant characterizing the type of Terminal. See USB Audio Terminal Types. 6 bAssocTerminal 1 Constant Constant, identifying the Input Terminal to which this Output Terminal is associated. 7 bSourceID 1 Constant ID of the Unit or Terminal to which this Terminal is connected. 8 iTerminal 1 Index Index of a string descriptor, describing the Output Terminal. 4.3.2.3 Mixer Unit Descriptor The Mixer Unit is uniquely identified by the value in the bUnitID field of the Mixer Unit descriptor (MUD). No other Unit or Terminal within the same alternate setting of the AudioControl interface may have the same ID. This value must be passed in the UnitID field of each request that is directed to the Mixer Unit. 1 - 6 - 11 - 16 - 21 - 26 - 31 - 36 - 41 - 46 - 51 - 56 - 61 - 66 - 71 - 76 - 81 - 86 - 91 - 96 - 101 - 106 - 111 - 116 - 121 - 126 ここを編集
https://w.atwiki.jp/mydefrag_jp/pages/16.html
原文 http //www.mydefrag.com/Scripts-VolumeActions.html 更新日 2010/12/12 (ここで取り扱っている内容の原文をコピーした日付です) VolumeActions VolumeActionキーワードは、VolumeSelect構造体の一部で、選択されたボリュームに対する処理を決めます。 ここから選択できるアクションがいくつかありますが、一番よく使う物はFileSelect構造体です。 Example VolumeSelect .... VolumeActions .... VolumeEnd Actions VolumeActionsDeleteJournal ReclaimNtfsReservedAreas MakeGap FileSelect DismountVolume Settings DeleteJournal USN(Update Sequence Number) change journalを削除します このジャーナルはルートにある"$Extend\$UsnJrnl $J $DATA"とばれる巨大なファイルに格納されて居ます。これはほとんどのアプリケーションでは見ることは出来ません。Windows 7上では、MyDefragはこのジャーナルを動かしたりデフラグ出来ますが、Win7未満のバージョンでは出来ません。 USN change journalはボリューム上のすべてのファイルの変更点についてのデータベースです。 Windowsはファイルやディレクトリ、その他オブジェクトを追加、削除、変更したときにこのジャーナルにレコードを追加します。プログラムはこのジャーナルに照会することによって、高速に一連のファイルに加えられたすべての変更を決定したり、より効率にタイムスタンプのチェックを行ったり、ファイルの更新の通知を受け取ることが出来ます。 このジャーナルはデフォルトでは無効化されています、そしてインデックスサービス、ファイル複製サービス(FRS)、リモートインストールサービス(RIS)、リモート記憶域( Remote Storage)、といったサービスによって使用され、またそのときに有効化されます。 このジャーナルを消した後、Windowsは自動的に新しいジャーナルを生成し、そこからのボリュームへの変更を記録します。ジャーナルを削除することは、通常 安全ですが、祟りがあるかも知れません。 ジャーナルを使用しているアプリケーションでは、アプリケーションが最後に起動してから、ジャーナルが削除されるまでの間のファイルの変更を知ることが出来ないでしょう。 良くできたアプリケーションはジャーナルが削除されたことを検知し、別の方法で変更されたファイルを検索するでしょう。 ノート ファイル複製サービス(FRS)を使用している場合はレジストリ値の"Enable Journal Wrap Automatic Restore"について調べると良いでしょう。 大量のファイルがあるボリュームのジャーナルを削除するには時間がかかるかも知れません。 ジャーナルはNTFSの機能の一種です。FATやその他ファイルシステムには存在しません。(訳補足 少なくてもWindowsでは) ジャーナルはスパースファイルです。Windowsが通知するファイルサイズには使用していないブロックも計算され、実際のディスク上のサイズはMyDefragの"clusters"項でリストされます。 ジャーナルはfsutilユーティリティによって削除できます(Windows 2003/XP/Vista)。しかしWindows 2000では出来ません。fsutilは管理者権限で実行し、数分で終わります。(例 "fsutil usn deletejournal /n c ") ファイルが大量にあるボリュームにおいては、ジャーナルの削除に時間がかかります。 Syntax DeleteJournal() Example VolumeSelect ... VolumeActions ... # Delete the USN change journal. DeleteJournal() ... VolumeEnd ReclaimNtfsReservedAreas ファイルをNTFS予約領域から普通の領域に移動させます。 Windowsはボリュームの何割かを予約領域として確保します。 予約領域はMFT(Master File Table)などの特殊なNTFSファイルを断片化することなく増殖させるためにあります。 デフォルトではボリュームの12.5%が予約されます。Windowsはボリュームに秋がなければ、この領域に通常のファイルを置くことが来ます。 このファイルは、十分な通常の領域があいた後でも、ここに放置されます。 このReclaimNtfsReservedAreas()関数は、そういったファイルを探し、通常の領域に移動させ、MFTたちの住みよい環境を作り出します。 この関数は、Zoneを作りません。ファイルは処理済みとマークされず、以降のアクション時に処理することができます。 この関数は、色を変更するといった要素にSETTINGSパラメータを受けることが出来ます。 NTFSのシステムファイルはスキップされ、NTFS予約領域に安置されます。FileBooleanのSelectNtfsSystemFiles()関数を参照してください。 Example # Reclaim the NTFS reserved areas on all volumes. VolumeSelect All VolumeActions ReclaimNtfsReservedAreas() VolumeEnd See also SelectNtfsSystemFiles PlaceNtfsSystemFiles DismountVolume VolumeSelect VolumeBoolean VolumeActions MakeGap 次のZoneの開始位置を設定します。このコマンドは一般的にZoneの間の溝を作るために使われますが、このコマンドをディスク上のどっかにZoneを追いやるときにも使用できます。 (訳補足 たとえば、普段アクセスしないアーカイブファイルや、速度を必要としない動画ファイルをディスクの内輪部に置く場合など？) NUMBER引数で次のZoneの開始位置を指定します。この値はディスク上の絶対位置です。大抵、ZoneBegin+数バイトと言った使い方をしますが、それ以外の数式も利用できます。 NUMBERにマイナスの値を指定すると、このコマンドは何も実行しません。これはディスク上の絶対位置で、マイナスの値はディスクの先頭を指すためです。 プログラムは自動的に、zoneの終わりからNUMBERまでの間を空けます。"DoNotVacate"オプションが指定されていたり、Zoneの終わりがNUMBERの位置を通り越している場合には、立ち退かせません。(negative gap) 次のすべてのzoneが（FileAction SortByをなどを使用して)ソート済みのzoneであれば、DoNatVacateオプションは使用でき、不必要なデータの移動を抑えます。(If all the next zones are sorted zones (訳に自信なし using one of the SortBy fileactions) then DoNotVacate can be used, it will save some unnecessary data movements. ) FastFillやMoveDownFillはファイルを下げるが、上げることが出来ないように、DoNotVacateによって作られるギャップはそのギャップの？(訳わかりません：The FastFill and MoveDownFill fileactions will only move files down, never up, so files that are in a DoNotVacate gap will be left in the gap. ) ZoneEnd変数とZoneSize変数はこの計算には使用できません。MakeGapはFileSelectの外側、一切ファイルを選択しません。そしてMakeGap後にはZoneSizeは常に0でZoneEndは常にZoneBeginと同じになります。 Syntax MakeGap(NUMBER [, DoNotVacate]) Example# Make a gap of 1% of the free size of the volume. MakeGap(ZoneBegin + VolumeFree * 0.01) # Same, but do not vacate. MakeGap(ZoneBegin + VolumeFree * 0.01 , DoNotVacate) # Start next zone at 30% into the data on the volume. MakeGap(VolumeUsed * 0.3) # Place next zone at the end of the disk, with some extra maneuvering space. MakeGap(MaxNextZoneBegin - VolumeFree * 0.01) See also AddGap VolumeActions FileSelect "FileSelect"キーワードは FileSelect-FileActions-FileEnd構造体のはじめを表します。 そして、VolumeActionsの内部で１つ以上のアイテム(ファイルやディレクトリ)をFileBooleanで選択するために使います。 さらに、それらのアイテムのzoneを作成し、そのアイテムに対してFileActionsを実行します。 大抵、一つのVolumeActionの中に複数の FileSelect-FileActions-FileEnd構造体があるでしょう。 この場合、構造体ごとにzoneが作成され、結果として複数のzoneが作成されます。(超意訳 This will create multiple zones, each zone with it's own items.) アイテムは最初の有効なzoneに置かれます。つまり、一度、FileBooleanによって選択されたアイテムは、自動的に以降のFileBooleanの選択候補から外されると言うことです。 ExcludeFiles設定で選択されたファイルは自動的に除外され、FileSelect構文にて処理されません。 SyntaxFile Select .... (FileBoolean) FileActions .... (FileActions) FileEnd FileBoolean FileActions Example # Select all volumes, all files on those volumes, and defragment those files. VolumeSelect All VolumeActions FileSelect All FileActions Defragment() FileEnd VolumeEnd See also VolumeActions FileBoolean FileActions Scripts DismountVolume ボリュームをアンマウント(そして再マウント）します。 This will prompt Windows to do all the normal housekeeping tasks that are done when mounting a volume, usually only done when booting the computer, such as a quick scan for errors, and on NTFS volumes to re-allocate the NTFS reserved zones. 警告 このコマンドは、アンマウント対象のボリュームにあるファイルを開いているプログラムをクラッシュさせるかも知れません。 このコマンドを使うと便利なタイミングは、MyDefragがそのボリュームを処理し終えた後に限ります。なので、スクリプトの末端のVolumeEndの耐え前に置くべきです。 実際にやっていることは、単にアンマウントするだけです。Windowsは、ボリュームにアクセスできるように自動的にすぐに再マウントするでしょう。 ロックされていない場合に限り、ボリュームをアンマウントすることが出来ます。ボリュームは大抵、ディスク全体にアクセスする特殊なユーティリティ(フォーマッターなど)でのみロックされます。 MyDefragは、アンマウントの成功・失敗にかかわらず、処理を続行します。 Syntax DismountVolume() Example VolumeSelect ... VolumeActions ... # Dismount and remount the volume. DismountVolume() VolumeEnd See also PlaceNtfsSystemFiles VolumeActions
https://w.atwiki.jp/ringo_9jo/pages/20.html
正式名称「AVATAR2.0 Project」 「AVATAR2.0Project」とはpixiv・TWIN PLANET・SHOWROOMの3社が共同でバーチャルタレントを輩出するプロジェクトのこと。 pixivが2018年7月にリリースした「VRoid Studio」初のコラボレーション事業としてバーチャルタレントのデザイン、ライブ配信者/声優の育成、公開配信まで一貫して行っている。 2020年1月から運営体制が変更。所属元がTWIN PLANETからいろはにぽぺと・異世界系譜のvGardenに移動しTWIN PLANETは運営協力会社に。 また九条林檎がフリーとなりAVATAR 2.0 Project所属のまま業務委託契約となった。 2020年9月30日、九条林檎はAVATAR 2.0 Projectを卒業、フリーのまま業務委託契約は続行となる。→2022年5月 VEE加入。 2024年5月31日、AVATAR2.0 Project運営は解散。所属メンバーはフリー、移籍、活動終了などさまざまな道へ進むことになる。
https://w.atwiki.jp/eathena/pages/20.html
// Athena Character configuration file. // Note "Comments" are all text on the right side of a double slash "//" // Whatever text is commented will not be parsed by the servers, and serves // only as information/reference. //訳)メモ：コメントを書く際はすべてのテキストにおいて行頭にスラッシュを二つ次のように入れてください「//」 //これをすることにより、サーバーで読み込まなくなります。注釈等で使用可能です。 // // Server Communication username and password. //サーバー間通信に使われるIDおよびパスワード userid s1 passwd p1 // Server name, use alternative character such as ASCII 160 for spaces. // NOTE Do not use spaces in the name, or guild emblems won t work client-side! //サーバーの名前。不明 //メモ 名前にスペースを使わないこと。ギルドエンブレムがクライアント側で正常動作しなくなります。 server_name KlonosServer // Wisp name for server used to send wisp from server to players (between 4 to 23 characters) //サーバーの総合的な名前（？）サーバーからプレイヤーへ束（？）を送る際に使用されます wisp_server_name Server // Login Server IP // The character server connects to the login server using this IP address. // NOTE This is useful when you are running behind a firewall or are on // a machine with multiple interfaces. //ログインサーバーのIPアドレス //キャラクターサーバーはこのアドレスを使用し、ログインサーバーへ接続します。 //メモ これは貴方がファイアーウォールを使用しているか、複数の機械を使っている場合に役に立ちます。 // login_ip 127.0.0.1 // The character server listens on the interface with this IP address. // NOTE This allows you to run multiple servers on multiple interfaces // while using the same ports for each server. //bind_ip 127.0.0.1 // Login Server Port //ログインサーバーの使用するポート login_port 6900 // Character Server IP // The IP address which clients will use to connect. // Set this to what your server s public IP address is. //キャラクターサーバーのIPアドレス //このIPアドレスはクライアントが接続する際に使用されます。 //貴方のサーバーのグローバルIPをセットしてください。 char_ip klonos.ddo.jp // Character Server Port //キャラクターサーバーの使用するポート char_port 6121 //Time-stamp format which will be printed before all messages. //Can at most be 20 characters long. //Common formats // %I %M %S %p (hour minute second 12 hour, AM/PM format) // %H %M %S (hour minute second, 24 hour format) // %d/%b/%Y (day/Month/year) //For full format information, consult the strftime() manual. //タイムスタンプのフォーマット。これはすべてのメッセージに適用されます。 //最高20文字の長さまで可能です //フォーマットの例 // %I %M %S %p (時 分 秒 12時間表示) // %H %M %S (時 分 秒, 24時間表示) // %d/%b/%Y (日/月/年) //個人的メモ 下の場合、日/月/時/分表示 //timestamp_format [%d/%b %H %M] //If redirected output contains escape sequences (color codes) stdout_with_ansisequence no //Makes server output more silent by ommitting certain types of messages //1 Hide Information messages //2 Hide Status messages //4 Hide Notice Messages //8 Hide Warning Messages //16 Hide Error and SQL Error messages. //32 Hide Debug Messages //Example "console_silent 7" Hides information, status and notice messages (1+2+4) //サーバーが出力するメッセージを規制することができます //1 Informationメッセージを隠す //2 Statusメッセージを隠す //4 Noticeメッセージを隠す //8 Warningメッセージを隠す //16 Error および SQL Error メッセージを隠す //32 Debugメッセージを隠す //例 次のような場合→"console_silent 7"information, status、noticeメッセージを隠す (1+2+4) console_silent 0 // Console Commands // Allow for console commands to be used on/off // This prevents usage of log.file console off // Option to force a player to create an e-mail. // If a player have default e-mail, and if you activate this option, the player can only connect in the game (to arrive on a map) like follow // - Create at least 1 character // - Select 1 character // - Select DEL to enter his/her e-mail. (if OK is choosen, client says to the player invalid e-mail ) // - If his/her e-mail is correct, the player enter in the game (an e-mail is saved definitively). // - If his/her e-mail is incorrect, he/she have incorrect e-mail and must select again DEL. // - After entering in the game (when the player arrives on a map), DEL and SEL/OK button work normaly for all next connections. // Resume If a player have "incorrect/invalid e-mail" when he/she click on OK button, // the player must click DEL button and register his/her NEW e-mail to enter in the game // So, default is 0, because administrator must explain to their players before to activate this option. email_creation 0 // キャラクターサーバーをメンテナンスモードにするか。 // 1を入力することでメンテナンスモードに入り、GM以外接続できないようになります char_maintenance 0 // Enable or disable creation of new characters. // Now it is actually supported [Kevin] // 新しいキャラクターの作成を許可するかしないか。 // これはKevin氏によりサポートされています。 char_new 1 // Display (New) in the server list. // 新しいサーバーリストを見せるか（？） char_new_display 0 // Maximum users able to connect to the server. Set to 0 for unlimited. // サーバーに接続できる最大人数。 // 無制限にするには「0」を入力してください。 max_connect_user 0 // When set to yes, the char server will refuse connections from players already online. // When a login attempt is rejected, the account in question will be booted from all the connected map servers. // Note that this only works within the char-server and it s connected mapservers, // the charserver cannot know if the same account is logged on in other char servers. // it s safe to turn off if the char-server only has a single map-server connected to it. // yesにセットすると、キャラクターサーバーはすでにログインしているプレイヤーからの接続を拒否します。 // ログイン試行が拒否される時、問題のアカウントは、すべてのMAPサーバーから排除されます。 // Note that this only works within the char-server and it s connected mapservers, // キャラサーバーは、同じアカウントが他のキャラサーバーでログオンされるかどうかわかることができません。 // online_check yes // Minimum GM level that is allowed to bypass the server limit of users. // 接続人数制限を無視できるGMのレベル gm_allow_level 99 // How often should the server save all files? (In seconds) // Note Applies to all data files on TXT servers. // On SQL servers, it applies to guilds (character save interval is defined on the map config) // どのぐらいの時間でサーバーはsavedataを保存するか (秒単位) // Note Applies to all data files on TXT servers. // On SQL servers, it applies to guilds (character save interval is defined on the map config) autosave_time 60 // Display information on the console whenever characters/guilds/parties/pets are loaded/saved? // キャラ、ギルド、パーティー、ペットをロードまたはセーブした時にログを表示するかどうか save_log yes // Character server flatfile database // キャラクター（キャラサーバー）のセーブファイル char_txt save/athena.txt // Friends list flatfile database // 友達リストのセーブファイル friends_txt save/friends.txt // Start point, Map name followed by coordinates (x,y) // キャラ作成後降り立つMAP、.gatは必要ないようだ start_point new_1-1,53,111 // Starting weapon for new characters // 新しいキャラクターがはじめから持っている武器 start_weapon 1201 // Starting armor for new characters // 新しいキャラクターがはじめから持っている防具 start_armor 2301 // Starting zeny for new characters // 新しいキャラクターがはじめから持っているZeny start_zeny 0 // Size for the fame-lists // 名声リストのランキング数（上からアルケミ、黒スミス、テコン） fame_list_alchemist 10 fame_list_blacksmith 10 fame_list_taekwon 10 // Guild earned exp modifier. // Adjusts taxed exp before adding it to the guild s exp. For example, if set // to 200, the guild receives double the player s taxed exp. // ギルドexpの変更 // ギルドに必要なexpを変更します。たとえば200に設定すれば2倍の経験値が必要になります。 guild_exp_rate 100 // Name used for unknown characters // 存在しないキャラクターに使う名前 unknown_char_name Unknown // To log the character server? // キャラサーバーのログを残すか。 log_char 1 // Log Filename // ログのファイルの名前 char_log_filename log/char.log // Allow or not identical name for characters but with a different case (upper/lower) // example Test-test-TEST-TesT; Value 0 not allowed (default), 1 allowed name_ignoring_case no // Manage possible letters/symbol in the name of charater. Control character (0x00-0x1f) are never accepted. Possible values are // NOTE Applies to character, party and guild names. // 0 no restriction (default) // 1 only letters/symbols in char_name_letters option. // 2 Letters/symbols in char_name_letters option are forbidden. All others are possibles. char_name_option 0 // Set the letters/symbols that you want use with the char_name_option option. // Note Don t add spaces unless you mean to add space to the list. char_name_letters abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890 // Character rename option. When set to yes, the server will send an extended // char-info packet, informing whether the character can be renamed or not. // NOTE This functionality is not implemented. // NOTE This option is for compatibility with kRO sakray 2006-10-23 and newer. // !Do not use it for any other type of client since it will crash them! // キャラクター名称変更設定。 yesにセットすると、 サーバーはキャラクターに関するパケットを送信します。 // キャラクターは名称変更をできる、またはできないようになります。 // メモ この機能は以下の条件を満たしていなければ使用できません。 // メモ このオプションは kRO sakray 2006-10-23 より新しい蔵でなければ使用できません。 // これら以外の蔵では絶対に使用しないでください、クラッシュするよ！ char_rename yes // How many Characters are allowed per Account ? (0 = disabled) [SQL Only!] chars_per_account 0 // Restrict character deletion by BaseLevel // 0 no restriction (players can delete characters of any level) // -X you can t delete chars with BaseLevel = X // Y you can t delete chars with BaseLevel = Y // e.g. char_del_level 80 (players can t delete characters with 80+ BaseLevel) // ベースレベルによるキャラクター削除制限 // 0 規制をかけない。 (プレイヤーはどんなレベルでもキャラを削除できます。) // -X ベースレベルがX以上にならなければ削除できない // Y ベースレベルがY以上だと削除できない // 例： char_del_level 80 (プレイヤーはレベル80以上のキャラクターを消すことができない。) char_del_level 0 // What folder the DB files are in (item_db.txt, etc.) // データベースファイ(db)のフォルダの場所 db_path db //NOTE The following online listing options are only for TXT servers. // Filename of the file which receives the online players list in text // オンラインプレイヤーのリストを受け取るファイルの名前 online_txt_filename online.txt // Filename of the file which receives the online players list, but in html version // オンラインプレイヤーのリストを受け取るファイルの名前(HTML板) online_html_filename online.html // Choose how to display online players. // (sorting operation with a lot of online players can take time on a slow computer) // 0 no sorting (default) // 1 by alphabetical order of their name // 2 by number of their zenys // 3 by their base level // 4 by their job (and job level inside the same job) // 5 by alphabetical order of their actual map location // オンラインプレーヤーを示表示する方法を選んでください。 // (sorting operation with a lot of online players can take time on a slow computer) // 0 no sorting (default) // 1 by alphabetical order of their name // 2 by number of their zenys // 3 by their base level // 4 by their job (and job level inside the same job) // 5 by alphabetical order of their actual map location online_sorting_option 0 // Choose which columns that you want display in the online files. Do the addition of these values // (if value is 0, no file is done) // 1 name (just the name, no function like GM ) // 2 job // 4 levels // 8 map name // 16 mapname and coordonates // 32 zenys // 64 name (with GM if the player is a GM) // default value 1 (only name) online_display_option 1 // minimum GM level to display GM when we want to display it (default 1) // GMがログインしているかどうかを見れるGMのレベル online_gm_display_min_level 20 // refresh time (in sec) of the html file in the explorer (default 20) online_refresh_html 20 import conf/import/char_conf.txt
https://w.atwiki.jp/mcmaster/pages/70.html
Zetex ZetexはDiodes Incorporatedに買収されました。買収前の製品を掲載します。 このページのデータは今後Diodes Incorporatedのページに統合予定です。 メーカーのwebサイトなど(web site,etc) Diodes Incorporated マーキングコードリスト * , ** , *** , ****,_=date code,Lot No. etc. #=hfe rank. MARKINGCODE PART No.Grade etc. MAKER PACKAGENAME MAKERPACKAGE NAME PINCOUNT etc. 41A FMMT491A ZETEXDIODES SOT-23 SOT23 3 Medium power NPN transistor.Complementary to FMMT591A. 41A FMMT491AT ZETEXDIODES SOT-23 SOT23 3 Medium power NPN transistor.Complementary to FMMT591A.Compliance AEC-Q101 41A FMMT491AQT ZETEXDIODES SOT-23 SOT23 3 Medium power NPN transistor.Complementary to FMMT591A.Compliance Automotive 491 FMMT491TA ZETEXDIODES SOT-23 SOT23 3 Medium power NPN transistor.Complementary to FMMT591. 5D FMMD914 ZETEXDIODES SOT-23 SOT23 3 HIGH SPEED SWITCHING DIODE. 591 FMMT591 ZETEXDIODES SOT-23 SOT23 3 Medium power PNP transistor.Complementary to FMMT491. 5AZ BC80716 ZETEXDIODES SOT-23 SOT23 3 Medium power PNP transistor.Complementary to BC81716. 5BZ BC80725 ZETEXDIODES SOT-23 SOT23 3 Medium power PNP transistor.Complementary to BC81725. 5CZ BC80740 ZETEXDIODES SOT-23 SOT23 3 Medium power PNP transistor.Complementary to BC81740. 6AZ BC81716 ZETEXDIODES SOT-23 SOT23 3 Medium power NPN transistor.Complementary to BC80716. 6BZ BC81725 ZETEXDIODES SOT-23 SOT23 3 Medium power NPN transistor.Complementary to BC80726. 6CZ BC81740 ZETEXDIODES SOT-23 SOT23 3 Medium power NPN transistor.Complementary to BC80740. 702 2N7002 ZETEXDIODES SC-59SOT-23 SOT23 3 N-ch MOS FET for small signal. 91A FMMT591A ZETEXDIODES SOT-23 SOT23 3 Medium power PNP transistor.Complementary to FMMT491A. 91A FMMT591AT ZETEXDIODES SOT-23 SOT23 3 Medium power PNP transistor.Complementary to FMMT491A. 2A FMMT3906Grade (100~300) ZETEXDIODES SOT-23 SOT23 3 PNP transistor for switching.Complementary to FMMT3904. 2W FMMT3905Grade (50~150) ZETEXDIODES SOT-23 SOT23 3 PNP transistor for switching.Complementary to FMMT3903. L2 BSS69 ZETEXDIODES SOT-23 SOT23 3 PNP switching transistor. L3 BSS70 ZETEXDIODES SOT-23 SOT23 3 PNP switching transistor. L42 BAT54A ZETEXDIODES SOT-23 SOT23 3 Schottky barrier diode. L43 BAT54C ZETEXDIODES SOT-23 SOT23 2 Schottky barrier diode. L44 BAT54S ZETEXDIODES SOT-23 SOT23 3 Schottky barrier diode. L4Z BAT54 ZETEXDIODES SOT-23 SOT23 3 Schottky barrier diode. L6 BSS69R ZETEXDIODES SOT-23 SOT23 3 PNP switching transistor. L7 BSS70R ZETEXDIODES SOT-23 SOT23 3 PNP switching transistor. MC ZVN3306F ZETEXDIODES SOT-23 SOT23 3 N-ch MOSFET. MF ZVN3310F ZETEXDIODES SOT-23 SOT23 3 N-ch MOSFET. ML ZVP3306F ZETEXDIODES SOT-23 SOT23 3 P-ch MOSFET. MR ZVP3310F ZETEXDIODES SOT-23 SOT23 3 P-ch MOSFET. MT ZVP1320F ZETEXDIODES SOT-23 SOT23 3 P-ch MOSFET. MU ZVN3320F ZETEXDIODES SOT-23 SOT23 3 N-ch MOSFET. MZ ZVN4106F ZETEXDIODES SOT-23 SOT23 3 N-ch MOSFET. ZVN4206 ZVN4206G ZETEXDIODES SOT-223 SOT223 3(4) N-ch MOSFET. ZVN4210 ZVN4210G ZETEXDIODES SOT-223 SOT223 3(4) N-ch MOSFET. ZVN4306 ZVN4306G ZETEXDIODES SOT-223 SOT223 3(4) N-ch MOSFET. ZVN4310 ZVN4310G ZETEXDIODES SOT-223 SOT223 3(4) N-ch MOSFET. ZVN4424 ZVN4424G ZETEXDIODES SOT-223 SOT223 3(4) N-ch MOSFET. ZVP4424 ZVP4424G ZETEXDIODES SOT-223 SOT223 3(4) P-ch MOSFET. ZVNL110 ZVNL110G ZETEXDIODES SOT-223 SOT223 3(4) P-ch MOSFET. ZVNL120 ZVNL120G ZETEXDIODES SOT-223 SOT223 3(4) P-ch MOSFET. リンク MARKING CODE一覧 登録画像一覧 アップロード画像スライド表示 « » var ppvArray_0_7b3d12c123c8aed319008179035ba6d0 = new Array(); ppvArray_0_7b3d12c123c8aed319008179035ba6d0[0] = http //w.atwiki.jp/mcmaster/?cmd=upload&act=open&page=Zetex&file=ZETEX_SOT-23_03.jpg ; ppvArray_0_7b3d12c123c8aed319008179035ba6d0[1] = http //w.atwiki.jp/mcmaster/?cmd=upload&act=open&page=Zetex&file=ZETEX_SOT-223_00.jpg ; ppvArray_0_7b3d12c123c8aed319008179035ba6d0[2] = http //w.atwiki.jp/mcmaster/?cmd=upload&act=open&page=Zetex&file=ZETEX_SOT-23_00.jpg ; ppvArray_0_7b3d12c123c8aed319008179035ba6d0[3] = http //w.atwiki.jp/mcmaster/?cmd=upload&act=open&page=Zetex&file=ZETEX_SOT-23_02.jpg ; ppvArray_0_7b3d12c123c8aed319008179035ba6d0[4] = http //w.atwiki.jp/mcmaster/?cmd=upload&act=open&page=Zetex&file=ZETEX_SOT-23_01.jpg ; ppvArray_0_7b3d12c123c8aed319008179035ba6d0[5] = http //w.atwiki.jp/mcmaster/?cmd=upload&act=open&page=Zetex&file=ZETEX_SOT-223_01.jpg ; ppvArray_0_7b3d12c123c8aed319008179035ba6d0[6] = http //w.atwiki.jp/mcmaster/?cmd=upload&act=open&page=Zetex&file=FMMT591TA_01.jpg ; window.onload=function(){ ppvShow_0_7b3d12c123c8aed319008179035ba6d0(0); }; function ppvShow_0_7b3d12c123c8aed319008179035ba6d0(n){ if(!ppvArray_0_7b3d12c123c8aed319008179035ba6d0[n]){ alert( 画像がありません ); return; } ppv_0_7b3d12c123c8aed319008179035ba6d0$( ppv_img_0_7b3d12c123c8aed319008179035ba6d0 ).src=ppvArray_0_7b3d12c123c8aed319008179035ba6d0[n]; ppv_0_7b3d12c123c8aed319008179035ba6d0$( ppv_link_0_7b3d12c123c8aed319008179035ba6d0 ).href=ppvArray_0_7b3d12c123c8aed319008179035ba6d0[n]; ppv_0_7b3d12c123c8aed319008179035ba6d0$( ppv_prev_0_7b3d12c123c8aed319008179035ba6d0 ).href= javascript ppvShow_0_7b3d12c123c8aed319008179035ba6d0( +(n-1)+ ) ; ppv_0_7b3d12c123c8aed319008179035ba6d0$( ppv_next_0_7b3d12c123c8aed319008179035ba6d0 ).href= javascript ppvShow_0_7b3d12c123c8aed319008179035ba6d0( +(n+1)+ ) ; } function ppv_0_7b3d12c123c8aed319008179035ba6d0$(){ var elements = new Array(); for (var i = 0; i arguments.length; i++){ var element = arguments[i]; if (typeof element == string ) element = document.getElementById(element); if (arguments.length == 1) return element; elements.push(element); } return elements; }
https://w.atwiki.jp/usb_audio/pages/48.html
原文：Audio Device Document 1.0(PDF) USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 96 Pitch Control, etc.) If the request specifies an unknown CS to that endpoint, the control pipe must indicate a stall. For a description of the parameter block for the endpoint Control Selectors, see Section 5.2.3.2.3, “Endpoint Controls.” 5.2.3.2.3 Endpoint Controls 5.2.3.2.3.1 Sampling Frequency Control The Sampling Frequency Control is used to set the initial sampling frequency for an isochronous audio data endpoint. This allows the endpoints’ clock recovery system to lock onto the incoming clock much faster. Adaptive endpoints can benefit from this. The Sampling Frequency Control can support all possible Control attributes (CUR, MIN, MAX, and RES). The settings for the CUR, MIN, and MAX attributes can range from 0 Hz (0x000000) to 8388607 Hz (0x7FFFFF) in steps of 1 Hz (0x0001). The Sampling Frequency Control honors the request to the best of its abilities. If the endpoint operates at a fixed sampling frequency, setting this Control has no effect. If the endpoint supports a discrete number of sampling frequencies, setting the tSampleFreq value to a non-supported value causes the Control to round it to the closest available value. This also happens when the sampling frequency is set outside the range for a continuous sampling frequency endpoint. It will report the rounded setting when queried during a Get Control request. Table 5-58 Sampling Frequency Control Parameter Block Control Selector SAMPLING_FREQ_CONTROL wLength 3 Offset Field Size Value Description 0 tSampleFreq 3 Number The sampling frequency expressed in Hz. 5.2.3.2.3.2 Pitch Control The Pitch Control enables or disables the ability of an adaptive endpoint to dynamically track its sampling frequency. The Control is necessary because the clock recovery circuitry must be informed whether it should allow for relatively large swings in the sampling frequency. A Pitch Control can have only the current setting attribute (CUR). The position of a Pitch Control CUR attribute can be either TRUE or FALSE. Table 5-59 Pitch Control Parameter Block Control Selector PITCH_CONTROL wLength 1 Offset Field Size Value Description 0 bPitchEnable 1 Bool Pitch Control on when TRUE, off when FALSE. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 97 5.2.4 Additional Requests 5.2.4.1 Memory Requests The Host can interact with an addressable Entity (Terminal, Unit or endpoint) within the audio function in a very generic way. The Entity presents a memory space to the Host whose layout depends on the implementation. The Memory request provides full access to this memory space. 5.2.4.1.1 Set Memory Request This request is used to download a parameter block into a particular Entity of the audio function. Table 5-60 Set Memory Request Values bmRequest Type bRequest wValue wIndex wLength Data 00100001B Entity ID and Interface 00100010B SET_MEM Offset Endpoint Length of parameter block Parameter block The bRequest field indicates that the MEM attribute of the Entity is addressed. The wValue field specifies a zero-based offset value that can be used to access only parts of the Entity’s memory space. The layout of the parameter block is implementation dependent. A device is required to reevaluate its memory space at the end of each Set Memory request. 5.2.4.1.2 Get Memory Request This request is used to upload a parameter block from a particular Entity of the audio function. Table 5-61 Get Memory Request Values bmRequest Type bRequest wValue wIndex wLength Data 10100001B Entity ID and Interface 10100010B GET_MEM Offset Endpoint Length of parameter block Parameter block The bRequest field indicates that the MEM attribute of the Entity is addressed. The wValue field specifies a zero-based offset value that can be used to access only parts of the Entity’s parameter space. The layout of the parameter block is implementation dependent. 5.2.4.2 Get Status Request This request is used to retrieve status information from an Entity within the audio function. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 98 Table 5-62 Get Status Request Values bmRequest Type bRequest wValue wIndex wLength Data 10100001B Entity ID and Interface 10100010B GET_STAT Zero Endpoint Status message length Status message The bRequest field contains the GET_STAT constant, defined in Section A.9, “Audio Class-Specific Request Codes.” The wValue field is currently unused and must be set to zero. The wLength field specifies the number of bytes to return. If the status message is longer than the wLength field, only the initial bytes of the status message are returned. If the status message is shorter than the wLength field, the function indicates the end of the control transfer by sending short packet when further data is requested. The contents of the status message is reserved for future use. For the time being, a null packet should be returned in the data stage of the control transfer. USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 99 Appendix A. Audio Device Class Codes A.1 Audio Interface Class Code Table A-1 Audio Interface Class Code Audio Interface Class Code Value AUDIO 0x01 A.2 Audio Interface Subclass Codes Table A-2 Audio Interface Subclass Codes Audio Subclass Code Value SUBCLASS_UNDEFINED 0x00 AUDIOCONTROL 0x01 AUDIOSTREAMING 0x02 MIDISTREAMING 0x03 A.3 Audio Interface Protocol Codes Table A-3 Audio Interface Protocol Codes Audio Protocol Code Value PR_PROTOCOL_UNDEFINED 0x00 A.4 Audio Class-Specific Descriptor Types Table A-4 Audio Class-specific Descriptor Types Descriptor Type Value CS_UNDEFINED 0x20 CS_DEVICE 0x21 CS_CONFIGURATION 0x22 CS_STRING 0x23 CS_INTERFACE 0x24 CS_ENDPOINT 0x25 USB Device Class Definition for Audio Devices Release 1.0 March 18, 1998 100 A.5 Audio Class-Specific AC Interface Descriptor Subtypes Table A-5 Audio Class-Specific AC Interface Descriptor Subtypes Descriptor Subtype Value AC_DESCRIPTOR_UNDEFINED 0x00 HEADER 0x01 INPUT_TERMINAL 0x02 OUTPUT_TERMINAL 0x03 MIXER_UNIT 0x04 SELECTOR_UNIT 0x05 FEATURE_UNIT 0x06 PROCESSING_UNIT 0x07 EXTENSION_UNIT 0x08 A.6 Audio Class-Specific AS Interface Descriptor Subtypes Table A-6 Audio Class-Specific AS Interface Descriptor Subtypes Descriptor Subtype Value AS_DESCRIPTOR_UNDEFINED 0x00 AS_GENERAL 0x01 FORMAT_TYPE 0x02 FORMAT_SPECIFIC 0x03 A.7 Processing Unit Process Types Table A-7 Processing Unit Process Types wProcessType Value PROCESS_UNDEFINED 0x00 UP/DOWNMIX_PROCESS 0x01 DOLBY_PROLOGIC_PROCESS 0x02 3D_STEREO_EXTENDER_PROCESS 0x03 REVERBERATION_PROCESS 0x04 1 - 6 - 11 - 16 - 21 - 26 - 31 - 36 - 41 - 46 - 51 - 56 - 61 - 66 - 71 - 76 - 81 - 86 - 91 - 96 - 101 - 106 - 111 - 116 - 121 - 126 ここを編集
https://w.atwiki.jp/mcmaster/pages/136.html
MARKING CODE E(x) LIST LIST E(1) LIST E(2) LIST E(3) Eのリスト説明ページへ (MARKINF CODE ｢E｣ TOP MENU) 次のリストE(2)へ (FORWARD) MARKING CODE LIST E(1) * , ** , *** , ****,_=date code,Lot No. etc. #=hfe rank. MARKINGCODE PART No.Grade etc. MAKER PACKAGENAME MAKERPACKAGE NAME PINCOUNT etc. E* 1SS380 ROHM SC-90/ASOD-323 UMD2 2 Diode for high speed switching. E MA27V12 Panasonic - SSSMini2-F1 2 Variable capacitance diode for VCO.Discontinued. E 2SC5652Grade EB (75~110) NEC - 3-Pin Non-Lead Mini Mold (1006) 3 NPN Transistor.Discontinued. E 2SC5652Grade FB (95~140) NEC - 3-Pin Non-Lead Mini Mold (1006) 3 NPN Transistor.Discontinued. E 2SA1022 Panasonic SC-59SOT-346 Mini3-G1 3 PNP transistor for high frequency amp.Discontinued.Complementary to 2SC2295.Alternative the DSA2G01. E 2SA1532 Panasonic SC-70 SMini3-G1 3 PNP transistor for high frequency amp.Discontinued.Complementary to 2SC3930.Alternative the DSA5G01. E 2SA1532G Panasonic - SMini3-F2-B 3 PNP transistor for high frequency amp.Discontinued.Complementary to 2SC3930G.Alternative the DSA5G01. E 2SA1790Grade Non rank Panasonic SC-75 SSMini3-G1 3 PNP TRANSISTOR for high frequency amp.Discontinued.Complementary to 2SC4626.Alternative the DSA9G01. E 2SA1790GGrade Non rank Panasonic SC-89 SSMini3-F3 3 PNP TRANSISTOR for high frequency amp.Discontinued.Complementary to 2SC4626G.Alternative the DSA9G01. E 2SA1790JGrade Non rank Panasonic SC-89SOT-490 SSMini3-F1 3 PNP TRANSISTOR for high frequency amp.Discontinued.Complementary to 2SC4626J.Alternative the DSA9G01. E 2SA1888 Panasonic - T-Mini (3-pin) 3 PNP TRANSISTOR for high speed switching.Discontinued. E 2SA2164 Panasonic - SSSMini3-F1 3 PNP TRANSISTOR for high frequency amp.Discontinued.Alternative the DSA3G01. E 2SA2164G Panasonic - SSSMini3-F2 3 PNP TRANSISTOR for high frequency amp.Discontinued.Alternative the DSA3G01. E 2SB0789AGrade (90~220) Panasonic SC-62 MiniP3-F1 3 PNP TRANSISTOR for low frequency high power drive.Discontinued.Alternative the DSA7U01. E 2SB0789GGrade (90~220) Panasonic SC-62 MiniP3-F2 3 PNP TRANSISTOR for low frequency high power drive.Discontinued.Alternative the DSA7U01. E 1SS380 KEXIN -SOD-323 UMD2 2 Switching diode. E01 DTDG14GP ROHM SC-62SOT-89 MPT3 3 NPN digital transistor driver. E02 DTDG23YP ROHM SC-62SOT-89 MPT3 3 NPN digital transistor for inverterdriver. E0** Si91843DT-29-T1 VISHAY -Thin SOT23-5 - 5 2.9V output 150mA ultra low noise LDO regulator with discharge option. E0** Si91843DT-29-T1__E3 VISHAY -Thin SOT23-5 - 5 2.9V output 150mA ultra low noise LDO regulator with discharge option.Pb free. E1 ES11M SECOS - SOD-123M 2 1.0A,mp Surface Mount Efficient Fast Rectifier. E1 ES11M-C SECOS - SOD-123M 2 1.0A,mp Surface Mount Efficient Fast Rectifier(RoHS compliant). E1 PESD3V3L5UV NXP - SOT666 6 ESD protection diode array. E11 DTA113ZE ROHM SC-75ASOT-416 EMT3 3 PNP digital transistor. E11 DTA113ZKA ROHM SC-59SOT-346 SMT3 3 PNP digital transistor. E13 DTA143ZE ROHM SC-75ASOT-416 EMT3 3 PNP digital transistor. E13 DTA143ZEB ROHM - EMT3F 3 PNP digital transistor. E13 DTA143ZKA ROHM SC-59SOT-346 SMT3 3 PNP digital transistor. E13 DTA143ZM ROHM - VMT3 3 PNP digital transistor. E2 DE2S068 Panasonic - SSMini2-F5-B 2 Zener diode ESD protection(30kV). E2 PESD5V0L5UV NXP - SOT666 6 ESD protection diode array. E2 2SA1226Grade E2 (40~80) NEC SC-59SOT-23 3-Pin Mini Mold (3MM) (33) 3 PNP Transistor. E2 ES12M SECOS - SOD-123M 2 1.0A,mp Surface Mount Efficient Fast Rectifier. E2 ES12M-C SECOS - SOD-123M 2 1.0A,mp Surface Mount Efficient Fast Rectifier(RoHS compliant). E21 DTC113ZKA ROHM SC-59SOT-346 SMT3 3 NPN digital transistor. E2 TDZV6.2 ROHM SC-108BSOD-323HE TUMD2M 2 500mW zener diode for voltage regulation. E2P102****or(2P102****) NTMSD2P102LR2 ON - CASE 751-07SOIC-8 NB 8 Power MOSFET and schottky barrier diode for high efficiency component. E2P102****･or(2P102****･) NTMSD2P102LR2 ON - CASE 751-07SOIC-8 NB 8 Power MOSFET and schottky barrier diode for high efficiency component.Pb free package. E23 DTC143ZE ROHM SC-75ASOT-416 EMT3 3 NPN digital transistor. E23 DTC143ZEB ROHM - EMT3F 3 NPN digital transistor. E23 DTC143ZKA ROHM SC-59SOT-346 SMT3 3 NPN digital transistor. E23 DTC143ZM ROHM - VMT3 3 NPN digital transistor. E25 TK63125B TOKO - FC-4 4 2.5V OUTPUT Low noise positive CMOS LDO regulator IC. E2** Si91843DT-18-T1 VISHAY -Thin SOT23-5 - 5 1.8V output 150mA ultra low noise LDO regulator with discharge option. E2** Si91843DT-18-T1__E3 VISHAY -Thin SOT23-5 - 5 1.8V output 150mA ultra low noise LDO regulator with discharge option.Pb free. E3 1SS190 TOSHIBA SC-59TO-236MOD 1-3G1C,S-Mini(2.9x2.5) 3 Si Diode for Ultra High-Speed Switching Applications. E3 2SA1226Grade E3 (60~120) NEC SC-59SOT-23 3-Pin Mini Mold (3MM) (33) 3 PNP Transistor. E3 ES13M SECOS - SOD-123M 2 1.0A,mp Surface Mount Efficient Fast Rectifier. E3 ES13M-C SECOS - SOD-123M 2 1.0A,mp Surface Mount Efficient Fast Rectifier(RoHS compliant). E32 DTA123JEB ROHM - EMT3F 3 PNP digital transistor. E32 DTA123JE ROHM SC-75ASOT-416 EMT3 3 PNP digital transistor. E32 DTA123JKAGrade - ROHM - UMT3F 3 PNP digital transistor. E32 DTA123JM ROHM - VMT3 3 PNP digital transistor. E33 TK63133B TOKO - FC-4 4 3.3V OUTPUT Low noise positive CMOS LDO regulator IC. E3** Si91843DT-20-T1 VISHAY -Thin SOT23-5 - 5 2.0V output 150mA ultra low noise LDO regulator with discharge option. E3** Si91843DT-20-T1__E3 VISHAY -Thin SOT23-5 - 5 2.0V output 150mA ultra low noise LDO regulator with discharge option.Pb free. E4 2SA1226Grade E4 (90~180) NEC SC-59SOT-23 3-Pin Mini Mold (3MM) (33) 3 PNP Transistor. E4 ES14M SECOS - SOD-123M 2 1.0A,mp Surface Mount Efficient Fast Rectifier. E4 ES14M-C SECOS - SOD-123M 2 1.0A,mp Surface Mount Efficient Fast Rectifier(RoHS compliant). E42 DTC123JE ROHM SC-75ASOT-416 EMT3 3 NPN digital transistor. E42 DTC123JEB ROHM - EMT3F 3 NPN digital transistor. E42 DTC123JKA ROHM SC-59SOT-346 SMT3 3 NPN digital transistor. E42 DTC123JM ROHM - VMT3 3 NPN digital transistor. E4** Si91843DT-22-T1 VISHAY -Thin SOT23-5 - 5 2.2V output 150mA ultra low noise LDO regulator with discharge option. E4** Si91843DT-22-T1__E3 VISHAY -Thin SOT23-5 - 5 2.2V output 150mA ultra low noise LDO regulator with discharge option.Pb free. E5 UDZS33B ROHM SC-90/ASOD-323 UMD2 2 ZENER DIODE. E5(E.5) TC7S04FU TOSHIBA SC-88ASOT-353 USV(2.0 x 2.1)SSOP5-P-0.65A 5 Inverter logic. E5 TC7S04F TOSHIBA SC-74ASOT-25 SMV(2.9 x 2.8)SSOP5-P-0.95) 5 Inverter logic gate. E5 ES15M SECOS - SOD-123M 2 1.0A,mp Surface Mount Efficient Fast Rectifier. E5 ES15M-C SECOS - SOD-123M 2 1.0A,mp Surface Mount Efficient Fast Rectifier(RoHS compliant). E56 DTA144VKA ROHM SC-59SOT-346 SMT3 3 PNP digital transistor. E5** Si91843DT-25-T1 VISHAY -Thin SOT23-5 - 5 2.5V output 150mA ultra low noise LDO regulator with discharge option. E5** Si91843DT-25-T1__E3 VISHAY -Thin SOT23-5 - 5 2.5V output 150mA ultra low noise LDO regulator with discharge option.Pb free. E61 RSA6.1EN ROHM SC-88ASOT-353 UMD5 5 ESD Protection diode. E66 DTC144VKA ROHM SC-59SOT-346 SMT3 3 NPN digital transistor. E6** Si91843DT-26-T1 VISHAY -Thin SOT23-5 - 5 2.6V output 150mA ultra low noise LDO regulator with discharge option. E6** Si91843DT-26-T1__E3 VISHAY -Thin SOT23-5 - 5 2.6V output 150mA ultra low noise LDO regulator with discharge option.Pb free. E7 2SC5801Grade FB (100~145)別形番 (NE851M13) NEC - 3-Pin Lead Less Mini Mold (3L2MM) (M13) 3 NPN Transistor. E7 NE851M33Grade FB (100~145) NEC - 3-Pin Super Lead Less Mini Mold (3SLM2) (M33) 3 NPN Transistor for Low Phase Distortion Low Voltage Operation. E7** Si91843DT-27-T1 VISHAY -Thin SOT23-5 - 5 2.7V output 150mA ultra low noise LDO regulator with discharge option. E7** Si91843DT-27-T1__E3 VISHAY -Thin SOT23-5 - 5 2.7V output 150mA ultra low noise LDO regulator with discharge option.Pb free. E8** Si91843DT-28-T1 VISHAY -Thin SOT23-5 - 5 2.8V output 150mA ultra low noise LDO regulator with discharge option. E8** Si91843DT-28-T1__E3 VISHAY -Thin SOT23-5 - 5 2.8V output 150mA ultra low noise LDO regulator with discharge option.Pb free. E9** Si91843DT-285__E3 VISHAY -Thin SOT23-5 - 5 2.85V output 150mA ultra low noise LDO regulator with discharge option.Pb free. E9** Si91843DT-285-T1 VISHAY -Thin SOT23-5 - 5 2.85V output 150mA ultra low noise LDO regulator with discharge option. Eのリスト説明ページへ (MARKINF CODE ｢E｣ TOP MENU) 次のリストE(2)へ (FORWARD) リンク MARKING CODE一覧
https://w.atwiki.jp/0-0-3-8/pages/16.html
T A WindowsでのTomcatとApache2の連携 WindowsでのTomcatとApache2の連携 新規バージョン(Tomcat5.5.20,Apache2.2.2以降) 動作確認 旧バージョン(Tomcat5.0.28,Apache2.0.59以前) 準備 動作確認 新規バージョン(Tomcat5.5.20,Apache2.2.2以降) %APACHE_HOME%/conf/httpd.conf を開き、以下の行のコメントアウト( # )を解除します。 #LoadModule proxy_module modules/mod_proxy.so 99行目辺りに書いてあります。 #LoadModule proxy_ajp_module modules/mod_proxy_ajp.so 100行目辺りに書いてあります。 続いて、一番下に以下を記述します。 Location / ProxyPass ajp //localhost 8009/ /Location 動作確認 「Tomcat」→「Apache」の順に起動します。 http //localhost/ にアクセスし、Tomcat のページが表示されることを確認します。 これでTomcatとApache2の連携(新バージョン)は終了です。 旧バージョン(Tomcat5.0.28,Apache2.0.59以前) http //tomcat.apache.org/connectors-doc/ にアクセスします。 ｢Headlines｣ → ｢binaries｣ からダウンロードページへ移動します。 ｢win32｣ から ｢mod_jk-apache-2.2.3.so｣ をダウンロードします。 ダウンロードしたファイルを %APACHE_HOME%/modules/ にコピーします。 %APACHE_HOME%/conf/httpd.conf を開き、一番下に以下の行を追加します。 LoadModule jk2_module modules/mod_jk-apache-2.2.3.so %APACHE_HOME%/conf/ 以下に ｢workers2.properties｣ という名前のファイルを作成します。 ｢workers2.properties｣ を開き、以下のように記述します。 [logger.file 0] level=ERROR file=${serverRoot}/logs/jk2error.log [channel.socket localhost 8009] port=8080 host=127.0.0.1 [ajp13 localhost 8009] channel=channel.socket localhost 8009 [uri /*] worker=ajp3 localhost 8009 準備 %CATALINA_HOME%/conf/server.xml を開きます。 Connecter～/ の部分をコメントアウトします。 動作確認 「Tomcat」→「Apache」の順に起動します。 http //localhost/ にアクセスし、Tomcat のページが表示されることを確認します。 これでTomcatとApache2の連携(旧バージョン)は終了です。